Server for wireless application service system

ABSTRACT

A wireless client device includes a receiver, controller, and transmitter. The receiver is configured to wirelessly receive a beacon from a wireless access point. The beacon includes an information element indicating whether the wireless access point is capable of providing a wireless application service. The controller is configured to, in response to the information element indicating that the wireless access point is capable of providing a wireless application service, generate a wireless application service request. The wireless application service request identifies a requested wireless application service, and identifies a source of an application to be obtained, installed, and executed by the wireless access point. Execution of the application enables the wireless access point to provide the requested wireless application service to the wireless client device. The transmitter is configured to wirelessly transmit a packet to the wireless access point. The packet includes the wireless application service request.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. patent application Ser. No. 13/568,617,filed on Aug. 7, 2012, which is a continuation of U.S. patentapplication Ser. No. 11/821,482 (now U.S. Pat. No. 8,238,889), filed onJun. 23, 2007, which claims the benefit of U.S. Provisional PatentApplication No. 60/910,947, filed on Apr. 10, 2007. The entiredisclosures of the above applications are incorporated by referenceherein.

BACKGROUND

The present invention relates generally to data communications. Moreparticularly, the present invention relates to a wireless applicationservice system.

SUMMARY

In general, in one aspect, the invention features an apparatuscomprising: a first network interface comprising a transmitter towirelessly transmit a beacon comprising an indication of the capabilityof the apparatus to provide wireless application services; a receiver towirelessly receive a wireless application service request from awireless client, the wireless application service request comprising arequest for one of the wireless application services, and an identifierof a service access point for the requested wireless applicationservice; a second network interface to obtain an application for therequested wireless application service from the service access point inresponse to the wireless application service request; and a processor toexecute the application, wherein the application provides the requestedwireless application service to the wireless client.

Some embodiments comprise a wireless access point comprising theapparatus. In some embodiments, the wireless access point is compliantwith all or part of IEEE standard 802.11, including draft and approvedamendments 802.11a, 802.11b, 802.11e, 802.11g, 802.11i, 802.11k,802.11n, 802.11v, and 802.11w. Some embodiments comprise a memory tostore data for the application. In some embodiments, the wirelessapplication service request further comprises one or more of: aclass-of-device identifier for the wireless client; a vendor identifierfor the wireless client; and a capabilities identifier for the wirelessclient. In some embodiments, the processor determines whether thewireless application service request is to be granted; and wherein thetransmitter wirelessly transmits a wireless application service requestresponse to the wireless client indicating whether the wirelessapplication service request is granted. In some embodiments, thereceiver wirelessly receives an authentication request from the wirelessclient; wherein the processor generates an authentication result basedon the authentication request; and wherein the transmitter wirelesslytransmits an authentication response to the wireless client, theauthentication response representing the authentication result. Someembodiments comprise a user interface comprising an authenticationdevice to authenticate a user of the user interface. In someembodiments, the authentication device comprises: a fingerprint reader.

In general, in one aspect, the invention features a method comprising:wirelessly transmitting, from an apparatus, a beacon comprising anindication of the capability of the apparatus to provide wirelessapplication services; wirelessly receiving a wireless applicationservice request from a wireless client, the wireless application servicerequest comprising a request for one of the wireless applicationservices, and an identifier of a service access point for the requestedwireless application service; obtaining an application for the requestedwireless application service from the service access point in responseto the wireless application service request; and executing theapplication, wherein the application provides the requested wirelessapplication service to the wireless client.

In some embodiments, a wireless access point comprises the apparatus. Insome embodiments, the wireless access point is compliant with all orpart of IEEE standard 802.11, including draft and approved amendments802.11a, 802.11b, 802.11e, 802.11g, 802.11i, 802.11k, 802.11n, 802.11v,and 802.11w. Some embodiments comprise storing data in the apparatus forthe application. In some embodiments, the wireless application servicerequest further comprises one or more of: a class-of-device identifierfor the wireless client; a vendor identifier for the wireless client;and a capabilities identifier for the wireless client. Some embodimentscomprise determining whether the wireless application service request isto be granted; and wirelessly transmitting a wireless applicationservice request response to the wireless client indicating whether thewireless application service request is granted. Some embodimentscomprise wirelessly receiving an authentication request from thewireless client; generating an authentication result based on theauthentication request; and wirelessly transmitting an authenticationresponse to the wireless client, the authentication responserepresenting the authentication result.

In general, in one aspect, the invention features a computer-readablemedia embodying instructions executable by a computer to perform amethod comprising: causing wireless transmission, from an apparatus, ofa beacon comprising an indication of the capability of the apparatus toprovide wireless application services, wherein the apparatus wirelesslyreceives a wireless application service request from a wireless client,the wireless application service request comprising a request for one ofthe wireless application services, and an identifier of a service accesspoint for the requested wireless application service; obtaining anapplication for the requested wireless application service from theservice access point in response to the wireless application servicerequest; and executing the application, wherein the application providesthe requested wireless application service to the wireless client.

In some embodiments, a wireless access point comprises the apparatus. Insome embodiments, the wireless access point is compliant with all orpart of IEEE standard 802.11, including draft and approved amendments802.11a, 802.11b, 802.11e, 802.11g, 802.11i, 802.11k, 802.11n, 802.11v,and 802.11w. In some embodiments, the method further comprises: storingdata in the apparatus for the application. In some embodiments, thewireless application service request further comprises one or more of: aclass-of-device identifier for the wireless client; a vendor identifierfor the wireless client; and a capabilities identifier for the wirelessclient. In some embodiments, the method further comprises: determiningwhether the wireless application service request is to be granted; andcausing wireless transmission of a wireless application service requestresponse to the wireless client indicating whether the wirelessapplication service request is granted. In some embodiments, the methodfurther comprises: generating an authentication result based on anauthentication request wirelessly received from the wireless client; andcausing wireless transmission of an authentication response to thewireless client, the authentication response representing theauthentication result.

In general, in one aspect, the invention features an apparatuscomprising: means for wirelessly transmitting a beacon comprising anindication of the capability of the apparatus to provide wirelessapplication services; means for wirelessly receiving a wirelessapplication service request from a wireless client, the wirelessapplication service request comprising a request for one of the wirelessapplication services, and an identifier of a service access point forthe requested wireless application service; means for obtaining anapplication for the requested wireless application service from theservice access point in response to the wireless application servicerequest; and means for executing the application, wherein theapplication provides the requested wireless application service to thewireless client.

Some embodiments comprise a wireless access point comprising theapparatus. In some embodiments, the wireless access point is compliantwith all or part of IEEE standard 802.11, including draft and approvedamendments 802.11a, 802.11b, 802.11e, 802.11g, 802.11i, 802.11k,802.11n, 802.11v, and 802.11w. Some embodiments comprise means forstoring data for the application. In some embodiments, the wirelessapplication service request further comprises one or more of: aclass-of-device identifier for the wireless client; a vendor identifierfor the wireless client; and a capabilities identifier for the wirelessclient. In some embodiments, the means for executing determines whetherthe wireless application service request is to be granted; and whereinthe means for wirelessly transmitting transmits a wireless applicationservice request response to the wireless client indicating whether thewireless application service request is granted. In some embodiments,the means for receiving wirelessly receives an authentication requestfrom the wireless client; wherein the means for executing generates anauthentication result based on the authentication request; and whereinmeans for wirelessly transmitting wirelessly transmits an authenticationresponse to the wireless client, the authentication responserepresenting the authentication result. Some embodiments comprise meansfor authenticating a user of the apparatus.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features will beapparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a wireless application service system according toembodiments of the present invention.

FIG. 2 shows a process for the wireless application service system ofFIG. 1 according to some embodiments of the present invention.

FIG. 3 shows the format of an information element (IE) according to someembodiments of the present invention.

FIG. 4 shows the format of a wireless application service requestaccording to some embodiments of the present invention.

FIG. 5 shows the format of a TLV field according to some embodiments ofthe present invention.

FIG. 6 shows the format of a wireless application service requestresponse according to some embodiments of the present invention.

FIG. 7 shows the format of an authentication request according to someembodiments of the present invention.

FIG. 8 shows the format of an authentication response according to someembodiments of the present invention.

FIGS. 9A-9E show various exemplary implementations of the presentinvention.

The leading digit(s) of each reference numeral used in thisspecification indicates the number of the drawing in which the referencenumeral first appears.

DESCRIPTION

As used herein, the terms “client” and “server” generally refer to anelectronic device or mechanism, and the term “message” generally refersto an electronic signal representing a digital message. As used herein,the term “mechanism” refers to hardware, software, or any combinationthereof. These terms are used to simplify the description that follows.The clients, servers, and mechanisms described herein can be implementedon any standard general-purpose computer, or can be implemented asspecialized devices. Furthermore, while some embodiments of the presentinvention are described with reference to a client-server paradigm,other embodiments employ other paradigms, such as peer-to-peer paradigmsand the like.

Embodiments of the present invention provide a wireless applicationservice system. The wireless application service system can include awireless client to request wireless application services and a wirelessaccess point to advertise and provide wireless application services. Forexample, a television remote control can include the wireless client.When the remote control detects an advertisement for a television guideservice, the remote control can request the television guide service.The wireless access point obtains a television guide application from aservice access point specified by the request, and executes theapplication, which provides the television guide service wirelessly tothe remote control.

In some embodiments, a wireless client wirelessly receivesadvertisements for one or more wireless application services. Forexample, a beacon transmitted by a wireless access point can include anindication of the capability of the wireless access point to providewireless application services. The wireless client can wirelesslytransmit a request to the wireless access point for one of the wirelessapplication services. The request can include an identifier of a serviceaccess point for the requested wireless application service.

In response, the wireless access point obtains an application for thewireless application service from the service access point and executesthe application. The application provides the wireless applicationservice to the wireless client. In some embodiments, the wireless clientmust be authenticated by the wireless access point before the wirelessapplication service is provided.

FIG. 1 shows a wireless application service system 100 according toembodiments of the present invention. Although in the describedembodiments, the elements of wireless application service system 100 arepresented in one arrangement, other embodiments may feature otherarrangements, as will be apparent to one skilled in the relevant artsbased on the disclosure and teachings provided herein. For example, theelements of wireless application service system 100 can be implementedin hardware, software, or combinations thereof.

Referring to FIG. 1, wireless application service system 100 includes awireless device 128 comprising a wireless client 102 in communication awith a wireless access point 104 over a wireless local-area network(WLAN) 106. In some embodiments, WLAN 106 is compliant with all or partof IEEE standard 802.11, including draft and approved amendments such as802.11a, 802.11b, 802.11e, 802.11g, 802.11i, 802.11k, 802.11n, 802.11v,and 802.11w. However, while embodiments of the present invention aredescribed in terms of wireless access points 104 and wireless clients102, other sorts of wireless network devices can be used instead.Furthermore, while embodiments of the present invention are described interms of a WLAN 106, other sorts of wireless networks can be usedinstead.

Wireless application service system 100 also includes an applicationserver 108 in communication with wireless access point 104 over awide-area network (WAN) 110. However, while embodiments of the presentinvention are described in terms of a WAN 110, other sorts of networkscan be used instead.

Referring again to FIG. 1, wireless access point 104 includes a WLANinterface 112, a WAN interface 114, a processor 116, and a memory 118.WLAN interface 112 includes a transmitter 120 and a receiver 122.Wireless access point 104 can also include a user interface 136including a fingerprint reader 138 or other authentication device, forexample to enter fingerprints of users. The fingerprints can then beused to authenticate users when they employ wireless device 128 torespond to authentication challenges issued by wireless access point104, as described below. In some embodiments, WAN interface 114 iscompliant with all or part of IEEE standard 802.11, including draft andapproved amendments such as 802.11a, 802.11b, 802.11e, 802.11g, 802.11i,802.11k, 802.11n, 802.11v, and 802.11w.

Wireless device 128 includes a user interface 130, a controller 132, andwireless client 102. Wireless client 102 includes a receiver 124 and atransmitter 126. In some embodiments, receiver 124 and transmitter 126are compliant with all or part of IEEE standard 802.11, including draftand approved amendments such as 802.11a, 802.11b, 802.11e, 802.11g,802.11i, 802.11k, 802.11n, 802.11v, and 802.11w.

FIG. 2 shows a process 200 for wireless application service system 100of FIG. 1 according to some embodiments of the present invention.Although in the described embodiments, the elements of process 200 arepresented in one arrangement, other embodiments may feature otherarrangements, as will be apparent to one skilled in the relevant artsbased on the disclosure and teachings provided herein.

Referring to FIG. 2, transmitter 120 of WLAN interface 112 of wirelessaccess point 104 transmits wireless beacon signals (step 202). Eachbeacon signal can include one or more information elements (IE). In someembodiments, the beacon signals and information elements are compliantwith all or part of IEEE standard 802.11, including draft and approvedamendments such as 802.11a, 802.11b, 802.11e, 802.11g, 802.11i, 802.11k,802.11n, 802.11v, and 802.11w.

FIG. 3 shows the format of an information element (IE) 300 according tosome embodiments of the present invention. IE 300 begins with a one-byteElement ID 302 that can be used to identify a manufacturer of wirelessaccess point 104. Element ID 302 is followed by a one-byte length field304 that identifies the length of IE 302, a three-byte WAPOrganizationally Unique Identifier (OUI) 306 representing a manufacturerof wireless access point 104, a one-byte proprietary IE Type 308, and atwo-byte version field 310.

In some embodiments, Element ID 302 is used to advertise wirelessapplication services. That is, the value of Element ID 302 provides anindication of the capability of wireless access point 104 to providewireless application services. Referring again to FIG. 2, receiver 124of wireless client 102 receives the beacon signal, and determineswhether wireless access point 104 is capable of providing wirelessapplication services (step 204), for example by examining the value ofElement ID 302 in the beacon signal.

If wireless client 102 determines that wireless access point 104 iscapable of providing wireless application services (step 204),transmitter 126 of wireless client 102 can transmit a wirelessapplication service request to wireless access point 104 (step 206).Controller 132 generates a packet representing the wireless applicationservice request, and transmitter 126 transmits a wireless signalrepresenting the packet.

FIG. 4 shows the format of a wireless application service request 400according to some embodiments of the present invention. Wirelessapplication service request 400 begins with a six-byte destinationaddress (DA) 402 that includes the address of wireless access point 104,followed by a six-byte source address (SA) 404 that includes the addressof wireless client 102. Wireless application service request 400 alsoincludes a two-byte length field (Len.) 406, a 3-byte IEEE 802.2 LogicalLink Control (LLC) portion including a one-byte field 408 comprising thevalue 0xAA, another one-byte field 410 comprising the value 0xAA, and aone-byte field 412 comprising the value 0x03, a three-byte WAP OUI 414representing a manufacturer of wireless access point 104, a two-bytefield 416 comprising a frame type (which can have a value of 0x0001 fora wireless application service request 400), an identifier of a serviceaccess point for the wireless application service including a three-byteVendor OUI 418 of a vendor of the application(s) that provides therequested wireless application service(s) and a two-byte vendor portnumber 420 of a port where the application is available, avariable-length list 422 of one or more Tag Length Value (TLV) fieldseach representing one of the requested wireless application services,and a two-byte frame check sequence (FCS) 424. Other embodiments caninclude the same and/or different fields of the same or differentlengths in the same or different order.

FIG. 5 shows the format of a TLV field 500 according to some embodimentsof the present invention. TLV field 500 includes a 2-byte tag 502, atwo-byte length 504 representing a length of TLV field 500, and avariable value 506 representing a requested wireless applicationservice. Variable value 506 can also represent one or more of thefollowing: a class-of-device identifier for wireless client 102, avendor identifier for wireless client 102, and a capabilities identifierfor wireless client 102. Other embodiments can include the same and/ordifferent fields of the same or different lengths in the same ordifferent order.

Referring again to FIG. 2, receiver 122 of wireless access point 104receives the wireless application service request. In response to thewireless application service request, wireless access point 104determines whether the application(s) that provide the requestedwireless application service(s) are already installed in wireless accesspoint 104 (step 208). If not, WAN interface 114 of wireless access point104 obtains the required application(s) from application server 108,which is specified by the vendor service access point in the wirelessapplication service request (step 210). Processor 116 of wireless accesspoint 104 then installs and executes the obtained application(s) inwireless access point 104 (step 212). Transmitter 120 of wireless accesspoint 104 can then transmit a wireless application service requestresponse to wireless client 102 (step 214). Processor 116 generates apacket representing the wireless application service request response,and transmitter 120 transmits a wireless signal representing the packet.

FIG. 6 shows the format of a wireless application service requestresponse 600 according to some embodiments of the present invention.Wireless application service request response 600 begins with a six-bytedestination address (DA) 602 that includes the address of wirelessclient 102, followed by a six-byte source address (SA) 604 that includesthe address of wireless access point 104. Wireless application servicerequest response 600 also includes a two-byte length field (Len.) 606, a3-byte IEEE 802.2 Logical Link Control (LLC) portion including aone-byte field 608 comprising the value 0xAA, another one-byte field 610comprising the value 0xAA, and a one-byte field 612 comprising the value0x03, a three-byte WAP OUI 614 representing a manufacturer of wirelessaccess point 104, a two-byte field 616 comprising a frame type (whichcan have a value of 0x8001 for a wireless application service requestresponse 600), an identifier of a service access point for the wirelessapplication service including a three-byte Vendor OUI 618 of a vendor ofthe application(s) that provides the requested wireless applicationservice(s) and a two-byte vendor port number 620 of a port where theapplication is available, a variable length list 622 of one or more TagLength Value (TLV) fields each representing one of the requestedwireless application services, and a two-byte frame check sequence (FCS)624. Other embodiments can include the same and/or different fields ofthe same or different lengths in the same or different order.

The TLV fields in TLV list 622 can have the same format as TLV field 500of FIG. 5. Each TLV field in TLV list 622 can include information forone of the wireless application services specified in the TLV field(s)in the TLV list 422 of the corresponding wireless application servicerequest 400.

In some embodiments, wireless client 102 must be authenticated beforereceiving a wireless application service. In some cases, the applicationcan perform the authentication. In other cases, wireless access point104 can perform the authentication for the application. In such cases,wireless access point 104 determines whether authentication is required(step 216). If so, wireless access point 104 challenges wireless client102 (step 218). In response to the challenge, wireless client 102transmits an authentication request to wireless access point 104 (step220). In some embodiments, user interface 130 of wireless device 128includes a fingerprint reader 134 or other authentication device toauthenticate the user, for example before responding to the challenge.

FIG. 7 shows the format of an authentication request 700 according tosome embodiments of the present invention. Authentication request 700begins with a six-byte destination address (DA) 702 that includes theaddress of wireless access point 104, followed by a six-byte sourceaddress (SA) 704 that includes the address of wireless client 102.Authentication request 700 also includes a two-byte length field 706, a3-byte IEEE 802.2 Logical Link Control (LLC) portion including aone-byte field 708 comprising the value 0xAA, another one-byte field 710comprising the value 0xAA, and a one-byte field 712 comprising the value0x03, a three-byte WAP OUI 714 representing a manufacturer of wirelessaccess point 104, a two-byte field 716 comprising a frame type (whichcan have a value of 0x0002 for an authentication request 700), athree-byte Vendor OUI 718 representing a provider of the desiredwireless application service, a two-byte vendor port number 720, avariable-length security certificate 722, and a two-byte FCS 724. Otherembodiments can include the same and/or different fields of the same ordifferent lengths in the same or different order.

Referring again to FIG. 2, wireless access point 104 attempts toauthenticate wireless client 102 (step 222), for example using securitycertificate 722 of FIG. 7. Referring again to FIG. 2, wireless accesspoint 104 then sends an authentication response to wireless client 102(step 224).

FIG. 8 shows the format of an authentication response 800 according tosome embodiments of the present invention. Authentication response 800begins with a six-byte destination address (DA) 802 that includes theaddress of wireless client 102, followed by a six-byte source address(SA) 804 that includes the address of wireless access point 104.Authentication response 800 also includes a two-byte length field 806, a3-byte IEEE 802.2 Logical Link Control (LLC) portion including aone-byte field 808 comprising the value 0xAA, another one-byte field 810comprising the value 0xAA, and a one-byte field 812 comprising the value0x03, a three-byte WAP OUI 814 representing a manufacturer of wirelessaccess point 104, a two-byte field 816 comprising a frame type (whichcan have a value of 0x8002 for an authentication response 800), athree-byte Vendor OUI 818, a two-byte vendor port number 820, avariable-length authentication result 822 representing the success orfailure of the authentication attempt, and a two-byte FCS 824. Otherembodiments can include the same and/or different fields of the same ordifferent lengths in the same or different order.

Referring again to FIG. 2, if the authentication was successful (step224), the application(s), now executing on processor 116 of wirelessaccess point 104, provides the requested wireless application service(s)to wireless client 102 (step 226).

As an example of the operation of embodiments of the present invention,consider the case where a consumer has purchased a wireless device 128comprising a wireless client 102. User interface 130 includes an “easyconfiguration” button that, when pressed, initiates a configurationprocess such as process 200 of FIG. 2. When contacting applicationserver 108, wireless access point 104 can register wireless device 128with its vendor and obtain an application from the vendor to providewireless application services to wireless device 128. For example, thewireless services can install firmware, upgrades and the like inwireless device 128.

Referring again to FIG. 1, applications providing wireless applicationservices can use memory 118 of wireless access point 104 so that littlestorage is required in wireless device 128. In the example wherewireless device 128 is a television remote control having a displayscreen, the application can obtain preview clips of television shows,store the clips in memory 118, and stream the clips to the remotecontrol when needed.

FIGS. 9A-9E show various exemplary implementations of the presentinvention. Referring now to FIG. 9A, the present invention can beimplemented in a high definition television (HDTV) 912. The presentinvention may implement either or both signal processing and/or controlcircuits, which are generally identified in FIG. 9A at 913, a WLANinterface and/or mass data storage of the HDTV 912. The HDTV 912receives HDTV input signals in either a wired or wireless format andgenerates HDTV output signals for a display 914. In someimplementations, signal processing circuit and/or control circuit 913and/or other circuits (not shown) of the HDTV 912 may process data,perform coding and/or encryption, perform calculations, format dataand/or perform any other type of HDTV processing that may be required.

The HDTV 912 may communicate with mass data storage 915 that stores datain a nonvolatile manner such as optical and/or magnetic storage devices.The HDD may be a mini HDD that includes one or more platters having adiameter that is smaller than approximately 1.8″. The HDTV 912 may beconnected to memory 916 such as RAM, ROM, low latency nonvolatile memorysuch as flash memory and/or other suitable electronic data storage. TheHDTV 912 also may support connections with a WLAN via a WLAN networkinterface 917.

Referring now to FIG. 9B, the present invention implements a controlsystem of a vehicle 918, a WLAN interface and/or mass data storage ofthe vehicle control system. In some implementations, the presentinvention implements a powertrain control system 919 that receivesinputs from one or more sensors such as temperature sensors, pressuresensors, rotational sensors, airflow sensors and/or any other suitablesensors and/or that generates one or more output control signals such asengine operating parameters, transmission operating parameters, and/orother control signals.

The present invention may also be implemented in other control systems922 of the vehicle 918. The control system 922 may likewise receivesignals from input sensors 923 and/or output control signals to one ormore output devices 924. In some implementations, the control system 922may be part of an anti-lock braking system (ABS), a navigation system, atelematics system, a vehicle telematics system, a lane departure system,an adaptive cruise control system, a vehicle entertainment system suchas a stereo, DVD drive, compact disc system and the like. Still otherimplementations are contemplated.

The powertrain control system 919 may communicate with mass data storage925 that stores data in a nonvolatile manner. The mass data storage 925may include optical and/or magnetic storage devices including HDDsand/or DVD drives. The HDD may be a mini HDD that includes one or moreplatters having a diameter that is smaller than approximately 1.8″. Thepowertrain control system 919 may be connected to memory 926 such asRAM, ROM, low latency nonvolatile memory such as flash memory and/orother suitable electronic data storage. The powertrain control system919 also may support connections with a WLAN via a WLAN networkinterface 927. The control system 922 may also include mass datastorage, memory and/or a WLAN interface (all not shown).

Referring now to FIG. 9C, the present invention can be implemented in acellular phone 928 that may include a cellular antenna 929. The presentinvention may implement either or both signal processing and/or controlcircuits, which are generally identified in FIG. 9C at 930, a WLANinterface and/or mass data storage of the cellular phone 928. In someimplementations, the cellular phone 928 includes a microphone 931, anaudio output 932 such as a speaker and/or audio output jack, a display933 and/or an input device 934 such as a keypad, pointing device, voiceactuation and/or other input device. The signal processing and/orcontrol circuits 930 and/or other circuits (not shown) in the cellularphone 928 may process data, perform coding and/or encryption, performcalculations, format data and/or perform other cellular phone functions.

The cellular phone 928 may communicate with mass data storage 935 thatstores data in a nonvolatile manner such as optical and/or magneticstorage devices including HDDs and/or DVD drives. The HDD may be a miniHDD that includes one or more platters having a diameter that is smallerthan approximately 1.8″. The cellular phone 928 may be connected tomemory 936 such as RAM, ROM, low latency nonvolatile memory such asflash memory and/or other suitable electronic data storage. The cellularphone 928 also may support connections with a WLAN via a WLAN networkinterface 937.

Referring now to FIG. 9D, the present invention can be implemented in aset top box 938. The present invention may implement either or bothsignal processing and/or control circuits, which are generallyidentified in FIG. 9D at 939, a WLAN interface and/or mass data storageof the set top box 938. The set top box 938 receives signals from asource such as a broadband source and outputs standard and/or highdefinition audio/video signals suitable for a display 940 such as atelevision, a monitor and/or other video and/or audio output devices.The signal processing and/or control circuits 939 and/or other circuits(not shown) of the set top box 938 may process data, perform codingand/or encryption, perform calculations, format data and/or perform anyother set top box functions.

The set top box 938 may communicate with mass data storage 943 thatstores data in a nonvolatile manner. The mass data storage 943 mayinclude optical and/or magnetic storage devices including HDDs and/orDVD drives. The HDD may be a mini HDD that includes one or more plattershaving a diameter that is smaller than approximately 1.8″. The set topbox 938 may be connected to memory 942 such as RAM, ROM, low latencynonvolatile memory such as flash memory and/or other suitable electronicdata storage. The set top box 938 also may support connections with aWLAN via a WLAN network interface 943.

Referring now to FIG. 9E, the present invention can be implemented in amedia player 944. The present invention may implement either or bothsignal processing and/or control circuits, which are generallyidentified in FIG. 9E at 945, a WLAN interface and/or mass data storageof the media player 944. In some implementations, the media player 944includes a display 946 and/or a user input 947 such as a keypad,touchpad and the like. In some implementations, the media player 944 mayemploy a graphical user interface (GUI) that typically employs menus,drop down menus, icons and/or a point-and-click interface via thedisplay 946 and/or user input 947. The media player 944 further includesan audio output 948 such as a speaker and/or audio output jack. Thesignal processing and/or control circuits 945 and/or other circuits (notshown) of the media player 944 may process data, perform coding and/orencryption, perform calculations, format data and/or perform any othermedia player functions.

The media player 944 may communicate with mass data storage 949 thatstores data such as compressed audio and/or video content in anonvolatile manner. In some implementations, the compressed audio filesinclude files that are compliant with MP3 format or other suitablecompressed audio and/or video formats. The mass data storage 949 mayinclude optical and/or magnetic storage devices including HDDs and/orDVD drives. The HDD may be a mini HDD that includes one or more plattershaving a diameter that is smaller than approximately 1.8″. The mediaplayer 944 may be connected to memory 950 such as RAM, ROM, low latencynonvolatile memory such as flash memory and/or other suitable electronicdata storage. The media player 944 also may support connections with aWLAN via a WLAN network interface 951. Still other implementations inaddition to those described above are contemplated.

A number of implementations of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention.Accordingly, other implementations are within the scope of the followingclaims.

What is claimed is:
 1. A wireless client device comprising: a receiverconfigured to wirelessly receive a beacon from a wireless access point,wherein the beacon includes an information element indicating whetherthe wireless access point is capable of providing a wireless applicationservice; a controller configured to, in response to the informationelement indicating that the wireless access point is capable ofproviding a wireless application service, generate a wirelessapplication service request, wherein the wireless application servicerequest identifies a requested wireless application service, andidentifies a source of an application to be obtained, installed, andexecuted by the wireless access point, wherein execution of theapplication by the wireless access point enables the wireless accesspoint to provide the requested wireless application service to thewireless client device, and wherein the source of the application isseparate from the wireless access point; and a transmitter configured towirelessly transmit a packet to the wireless access point, wherein thepacket includes the wireless application service request.
 2. Thewireless client device of claim 1, wherein the source of the applicationin the wireless application service request includes a unique identifierof a vendor of the application.
 3. The wireless client device of claim2, wherein the unique identifier is a 3-byte organizationally uniqueidentifier (OUI).
 4. The wireless client device of claim 2, wherein thesource of the application in the wireless application service requestfurther includes an identifier of a port at the vendor from which theapplication can be obtained.
 5. The wireless client device of claim 4,wherein the identifier of the port is two bytes in length.
 6. Thewireless client device of claim 1, wherein the receiver is configured towirelessly receive a wireless application service response from thewireless access point, wherein the wireless application service responseidentifies the requested wireless application service.
 7. The wirelessclient device of claim 1, wherein the wireless application servicerequest identifies a plurality of requested wireless applicationservices including the requested wireless application service.
 8. Thewireless client device of claim 7, wherein the wireless applicationservice request includes a variable-length list of identifiers of theplurality of requested wireless application services.
 9. The wirelessclient device of claim 8, wherein the identifier of each of theplurality of requested wireless application services is transported in atag-length-value field in the variable-length list.
 10. The wirelessclient device of claim 1, wherein: the receiver is configured towirelessly receive an authentication challenge from the wireless accesspoint, the transmitter is configured to, in response to theauthentication challenge being received by the receiver, wirelesslytransmit an authentication request to the wireless access point, theauthentication request includes a security certificate, and therequested wireless application service is available to the wirelessclient device only in response to the wireless access point determiningthat authentication was successful based on the security certificate.11. A method of operating a wireless client device, the methodcomprising: wirelessly receiving a beacon from a wireless access point,wherein the beacon includes an information element indicating whetherthe wireless access point is capable of providing a wireless applicationservice; in response to the information element indicating that thewireless access point is capable of providing a wireless applicationservice, generating a wireless application service request, wherein thewireless application service request identifies a requested wirelessapplication service, identifies a source of an application to beobtained, installed, and executed by the wireless access point, whereinexecution of the application by the wireless access point enables thewireless access point to provide the requested wireless applicationservice to the wireless client device, and wherein the source of theapplication is separate from the wireless access point; and wirelesslytransmitting a packet to the wireless access point, wherein the packetincludes the wireless application service request.
 12. The method ofclaim 11, wherein the source of the application in the wirelessapplication service request includes a unique identifier of a vendor ofthe application.
 13. The method of claim 12, wherein the uniqueidentifier is a 3-byte organizationally unique identifier (OUI).
 14. Themethod of claim 12, wherein the source of the application in thewireless application service request includes an identifier of a port atthe vendor from which the application can be obtained.
 15. The method ofclaim 14, wherein the identifier of the port is two bytes in length. 16.The method of claim 11, further comprising wirelessly receiving awireless application service response from the wireless access point,wherein the wireless application service response identifies therequested wireless application service.
 17. The method of claim 11,wherein the wireless application service request identifies a pluralityof requested wireless application services including the requestedwireless application service.
 18. The method of claim 17, wherein thewireless application service request includes a variable-length list ofidentifiers of the plurality of requested wireless application services.19. The method of claim 18, wherein the identifier of each of theplurality of requested wireless application services is transported in atag-length-value field in the variable-length list.
 20. The method ofclaim 11, further comprising: wirelessly receiving an authenticationchallenge from the wireless access point; and in response to theauthentication challenge being received by the receiver, wirelesslytransmitting an authentication request to the wireless access point,wherein the authentication request includes a security certificate, andwherein the requested wireless application service is available to thewireless client device only in response to the wireless access pointdetermining authentication was successful based on the securitycertificate.